Automatic registration of asset tags based on crowd sourcing asset context

ABSTRACT

A server-implemented method for automatically registering an asset tag in a database is disclosed. One or more asset tag collision reports are received from at least one mobile device connected to the server, each report including a tag identifier of the asset tag that is wirelessly broadcast by the asset tag. A location of the asset tag is determined based on the one or more received asset tag collision reports. A first asset is selected from a set of unregistered assets that are identified as being deployed in the indoor facility based on determining that there is a match between the location of the asset tag and location information associated with the first asset. The asset tag is then registered in association with the first asset in the database.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 15/229,161, granted as U.S. Pat. No. 9,955,316 on Apr. 24,2018, the contents of which are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates to asset tracking, and more particularly,to systems and methods for tracking locations of assets in an enterpriseenvironment.

BACKGROUND

Various assets of an enterprise, such as inventory and equipment, may bedistributed and moved throughout the enterprise's facilities. Forexample, in a company office building or campus, physical assets may bedeployed to multiple different locations, relocated within the facility,or removed from the premises. Asset tracking and management systems canmonitor the movement of physical assets throughout a facility. Manualtracking of assets in a facility is generally a laborious process andcan be a significant drain on workplace productivity. On the other hand,installing complex and expensive hardware for tracking assets may not befeasible or practically desirable.

BRIEF DESCRIPTION OF DRAWINGS

Reference will now be made, by way of example, to the accompanyingdrawings which show example embodiments of the present application andin which:

FIG. 1 diagrammatically shows an asset tracking system for an indoorfacility in accordance with example embodiments of the presentdisclosure.

FIG. 2 shows, in flowchart form, an example method for registering anasset tag in accordance with example embodiments of the presentdisclosure.

FIG. 3 shows, in flowchart form, another example method for registeringan asset tag in accordance with example embodiments of the presentdisclosure.

FIG. 4 shows, in flowchart form, another example method for registeringan asset tag in accordance with example embodiments of the presentdisclosure.

Like reference numerals are used in the drawings to denote like elementsand features.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

In an aspect, the present disclosure describes a method for registeringan asset tag in a database, where the asset tag is used to track alocation of an asset in an indoor facility. The method includes:receiving, from at least one mobile device connected to the server via awireless communication network, one or more asset tag collision reports,each of the one or more asset tag collision reports including a tagidentifier of the asset tag, wherein the tag identifier is transmittedto the at least one mobile device in wireless signals broadcast by theasset tag; determining a location of the asset tag based on the one ormore received asset tag collision reports; selecting a first asset froma set of one or more unregistered assets that are identified as beingdeployed in the indoor facility based on determining that there is amatch between the location of the asset tag and location informationassociated with the first asset; and registering the asset tag inassociation with the first asset in the database.

In another aspect, the present disclosure describes a system forregistering and managing asset tags. The system includes: an asset tagfor use in tracking a location of an asset in an indoor facility; atleast one mobile device configured to detect wireless signals broadcastby the asset tag; and a server connected to the at least one mobiledevice via a wireless communication network. The server is configuredto: receive, from the at least one mobile device, one or more asset tagcollision reports, each of the one or more asset tag collision reportsincluding a tag identifier of the asset tag, wherein the tag identifieris transmitted to the at least one mobile device in wireless signalsbroadcast by the asset tag; determine a location of the asset tag basedon the one or more received asset tag collision reports; select a firstasset from a set of one or more assets that are identified as beingdeployed in the indoor facility based on determining that there is amatch between the location of the asset tag and location informationassociated with the first asset; and register the asset tag inassociation with the first asset in the database.

In yet another aspect, the present disclosure describes a non-transitorycomputer-readable medium storing processor-executable instructions for aserver to register an asset tag in a database. The instructions include:instructions to receive, from at least one mobile device connected tothe server via a wireless communication network, one or more asset tagcollision reports, each of the one or more asset tag collision reportsincluding a tag identifier of the asset tag, wherein the tag identifieris transmitted to the at least one mobile device in wireless signalsbroadcast by the asset tag; instructions to determine a location of theasset tag based on the one or more received asset tag collision reports;instructions to select a first asset from a set of one or moreunregistered assets that are identified as being deployed in the indoorfacility based on determining that there is a match between the locationof the asset tag and location information associated with the firstasset; and instructions to register the asset tag in association withthe first asset in the database.

Other example embodiments of the present disclosure will be apparent tothose of ordinary skill in the art from a review of the followingdetailed descriptions in conjunction with the drawings.

The present application makes reference to “defined area” of an indoorfacility. This term is intended to cover any space in an indoor facilitywhich has finite dimensions (e.g. area) and defined boundaries, such asa room, a passage, a workspace, etc. For example, geo-fences may bedefined within a facility to demarcate the boundaries of defined areas.An indoor positioning system or asset tracking and management system mayhave access to various floor plans of a facility, which may facilitateidentification of defined areas and structural relationships between thedefined areas.

The present application makes reference to the status of an asset or anasset tag as being “registered”. An asset tag is registered if a pairingof the asset tag with an associated asset is stored in a database thatis accessible by an asset tracking system. An unregistered asset tag isone that has not been registered. For example, if a deployed asset isretrofitted with an asset tag or if an asset is newly deployed with anasset tag, the asset tag may not have been registered. By registering anasset tag in association with an asset, the access tracking system canmonitor the movement of the asset by virtue of the mapping between thelocation of the asset tag (which may be determined based on broadcastsignals from the asset tag) and the location of the asset. Similarly, anasset is registered if a pairing of the asset with an associated assettag is stored in a database that is accessible by an asset trackingsystem.

Various asset tracking systems employ radio frequency identification(RFID) technologies for locating objects in GPS-denied environments,such as office buildings. In such systems, wireless RFID tags may beconnected to assets to assist in tracking the locations of the assetswithin an indoor facility. These dedicated tracking systems typicallyinvolve a plurality of RFID gateway readers and passive or active RFIDtags connected to assets. The readers continuously monitor the locationsof the assets by sending out trigger or polling signals to which thetags respond. Other asset tracking solutions, such as those based onnear field communication (NFC) or Bluetooth low energy (BLE)technologies, may also rely on the use of asset tags.

In order to track an asset using an asset tag, the asset tag isgenerally required to be registered in association with the asset, forexample, in a database maintained as part of an asset management system.In particular, each pairing of an asset with its associated asset tag isstored in a database that is accessible by the asset management system.Where a large number of asset tags are to be deployed in a facility,manual registration of each tracked asset with its associated asset tagcan be onerous and time-consuming. For example, the physical assets in afacility may be retrofitted with asset tags simply by connecting tags tothe assets. In particular, assets that have already been deployed in afacility may subsequently be adapted for tracking and management, byretrofitting with asset tags. However, such retrofitting may beundesirable if each pairing of an asset with its associated asset tag isrequired to be manually registered at the time of connecting the tags.

In one aspect, the present application proposes an asset tracking andmanagement system that uses crowd-sourcing to register asset tags inassociation with their respective assets. Rather than relying on manualregistration of asset tags prior to tracking of assets in a facility,the present system and methods use data collected from a plurality ofdevices in the facility to identify pairings of unregistered asset tagswith their associated assets. More specifically, the present system andmethods collect location data associated with user devices, in theirordinary use within the facility, that are in close proximity to one ormore asset tags being tracked, in order to approximate the locations ofthe asset tags. The asset tags can then be paired with their respectiveassets, based on matching the estimated locations of the asset tags withlocation information associated with the assets. In this way, pairingsof assets with their asset tags may be automatically built up andregistered with an asset tracking system as a result of the normaldisposition of user devices rather than express manual registration.

System Overview

Reference is first made to FIG. 1, which diagrammatically shows anexample embodiment of an asset tracking system 100 for an indoorfacility 110 (not shown). The asset tracking system 100 is connected toa network 10. The network 10 may include one or more wired or wirelesscommunication networks, or combinations of both. For example, thenetwork 10 may be a Wireless Local Area Network (WLAN) that conforms tothe IEEE 802.11 standards (sometimes referred to as Wi-Fi). The network10 includes one or more wireless access points (APs) 30, such as Wi-FiAPs, which can transmit and receive radio frequencies for communicationwith wireless-enabled devices. The wireless APs 30 provide wirelessconnectivity to mobile devices 20 and any computing devices within alocal coverage area (such as an indoor facility) that are equipped forwireless communication using a designated protocol, such as IEEE 802.11.In at least some embodiments, the wireless APs 30 are distributedthroughout the indoor facility 110 in known locations and each wirelessAP 30 may be configured to periodically broadcast an identifier uniqueto the AP 30.

The asset tracking system 100 includes one or more mobile devices 20. Invarious example embodiments, the mobile device 20 may be a multi-modecommunication device configured for both data and voice communication, amobile telephone (e.g. smartphone, cellular phone), a tablet computer(e.g. slate computer), a wearable electronic device (e.g. watch, smartglasses), a personal digital assistant (PDA), or a mobile computersystem such as a laptop or netbook. In the asset tracking system 100 ofFIG. 1, the mobile devices 20 are equipped for wireless communicationvia the wireless APs 30 and are capable of receiving broadcast messagesor signals output by the wireless APs 30. According to known techniques,a mobile device 20 can measure the relative received signal strength(RSSI) of detected signals from the wireless APs 30, as well as othersources of radio frequency transmission. The mobile devices 20 may sendand receive communication signals over the network 10 after the requirednetwork registration or activation procedures have been completed. Itwill be appreciated that the asset tracking system 100 may also includeone or more stationary electronic devices (not shown), such as desktopcomputers or voice-over-IP (VoIP) phones.

In at least some embodiments, the mobile devices 20 may be managed by aMobile Device Management (MDM) system. An MDM system includes a centralserver component, which administers and monitors the mobile devices 20,and a client component, which can be run on a mobile device 20 toreceive and execute management commands from the server component. TheMDM system enables an administration server to, among otherfunctionalities, configure and update device settings over-the-air,enforce security policies and compliance rules, and remotely deployapplications to end-users. Modern MDM systems are typically implementedvia device management software that can run on subscriber devices.

In some embodiments, a mobile device 20 may include an asset trackingapplication 21. The mobile device 20 may detect wireless signalsbroadcast by one or more asset tags 60 associated with assets 50 in theindoor facility 110. In particular, the asset tracking application 21may be configured to indicate RSSI measurements for wireless signalstransmitted by the one or more asset tags 60 deployed throughout theindoor facility.

In at least some embodiments, the mobile device 20 may include an indoorpositioning application 22. For example, in a network such as the WLANof FIG. 1, an indoor positioning application 22 may be configured todetect RSSI measurements for wireless signals from a plurality of APs.The indoor positioning application 22 can send the measured RSSI valuesto a remote server implementing an indoor positioning system. The servermay then perform the computational work of correlating the RSSI valuesmeasured by the mobile device 20 with wireless AP fingerprints that arethemselves correlated to a location in the indoor facility 110. In thismanner, the indoor positioning application 22 may determine, forexample, the current location of the mobile device 20. In some otherembodiments, the indoor positioning application 22 may itself attempt tocorrelate measured RSSI values with wireless AP fingerprint data for theindoor facility 110, without transmitting the RSSI measurements to aremote server. The wireless AP measurements may be obtained, forexample, from a chipset, such as a Wi-Fi chip.

Other techniques for indoor navigation may be implemented by the indoorpositioning application 22. For example, sensor data may be collectedfrom a plurality of built-in sensors on the mobile device 20, such asaccelerometers, gyroscopes and/or magnetometers, and processed by theindoor positioning application 22 for implementing a sensor fusionalgorithm. As a further example, the indoor positioning application 22may be configured to measure a round-trip time (RTT) to a plurality ofwireless APs, based on signals exchanged with the APs, in order toestimate a current position of the mobile device 20. In at least someembodiments, the indoor positioning application 22 may use one or morehybrid algorithms for determining positions within the indoor facility110. In particular, a combination of techniques that exploit propertiesof wireless signals received from wireless APs may be implemented by theindoor positioning application 22. For example, a hybrid RSSI-RTTlocalization technique may be employed for tracking the location of themobile device 20.

The asset tracking application 21 and the indoor positioning application22 may be standalone applications or integrated with one another. Forexample, the indoor positioning application 22 may be integrated intothe asset tracking application 21, allowing a graphical map interfacemodule of the asset tracking application 21 to display the relativeposition of the mobile device 20 with respect to one or more trackedassets 50 within the indoor facility 110.

The mobile device 20 may include a short-range wireless communicationinterface that provides for communication between the mobile device 20and different systems or devices, which need not necessarily be similardevices. For example, the short-range communication interface mayinclude an infrared device and associated circuits and components, or aBluetooth® module to provide for communication with similarly-enabledsystems and devices.

The asset tracking system 100 includes one or more asset tags 60associated with assets 50 that are deployed in the indoor facility 110.In an enterprise setting, various physical assets may be shared betweenmultiple employees or transferred from one employee to another. Inparticular, assets may be moved when needed by different individuals orprojects. For example, as illustrated in FIG. 1, the asset 50 may beoffice equipment. Such assets may be misplaced or not returned to theiroriginating locations after use, or deliberately relocated to newlocations within the indoor facility 110 (for example, after personnelchange). Asset tags can facilitate tracking the locations of assets bybroadcasting wireless signals which may be detected by variouscomponents of an asset tracking system.

The asset tag 60 includes a housing which provides a durable structureto hold the components of the asset tag 60. The housing of the asset tag60 may be integral with the asset 50 or may be secured to the asset 50by affixing to an exterior surface of the asset 50. For example, theasset tag 60 can be attached to an asset 50 using an adhesive strip onat least one surface of the housing of the asset tag 60. The asset tag60 may alternatively be built in to the asset 50 itself or enclosed in apackaging of the asset 50.

The asset tag 60 also includes a battery 62. The battery 62 powers thecomponents of the asset tag 60. In at least some embodiments, thebattery 62 is replaceable. The housing of the asset tag 60 may include abuilt-in indicator providing visual or auditory indication of the chargestate of the battery 62. For example, a light-emitting diode (LED)indicator may be turned on or set to blink when the detected level ofbattery charge falls below a threshold value.

When an asset tag 60 that is connected to an asset 50 is activated, theasset tag 60 may broadcast signals to indicate that it has been turnedon. The asset tag 60 may include at least one wireless transceiver 63for transmitting wireless signals. A signal broadcast by the asset tag60 may be received by one or more electronic devices within a vicinityof the asset 50. In at least some embodiments, the wireless transceiver63 may transmit signals using short-wavelength ultra-high frequency(UHF) radio waves. For example, the radio waves may be in theIndustrial, Scientific and Medical (ISM) 2.4 GHz short-range radiofrequency band. In some embodiments, the wireless transceiver 63 may bebased on the Bluetooth® Low Energy (BTLE) specification, which canprovide considerably reduced power consumption and cost compared toclassic Bluetooth® while maintaining a similar communication range. Itwill be appreciated that the asset tag 60 may also or alternativelyimplement other types of short-range radio frequency communicationprotocols, such as NFC. The asset tag 60 is capable of sending data toand receiving data from those electronic devices in the indoor facility110 that are equipped for wireless communication.

The asset tag 60 may also include one or more sensors. In at least someembodiments, the asset tag 60 includes an accelerometer 67. Theaccelerometer 67 is a device that generates an output signal independence on the acceleration of the accelerometer 67 and specifies themagnitude and/or direction of acceleration. The accelerometer 67 may beintegrated into the housing of the asset tag 60 and generateaccelerometer outputs based on movements of the asset tag 60.

The asset tag 60 may also include processing circuitry 64, memory 65 anda timer 66. The processing circuitry 64 may include any combination ofdigital or analog circuitry for receiving signals from the accelerometer67 and controlling operations of the transceiver 63 in accordance with adesired protocol of operation. Example operations are described below.In some embodiments, the processing circuitry 64 may include discretelogic components, a field programmable gate array (FPGA), an applicationspecific integrated circuit (ASIC), or other digital or analogcircuitry.

The timer 66 may be a separate circuit element that is coupled to theprocessing circuitry 64 and is capable of providing a timestamp for anevent associated with the asset tag 60. In some cases, the timer 66 isimplemented by the processing circuitry 64 instead of being a separateelement. In at least some embodiments, the processing circuitry 64 maybe coupled to one or more of the wireless transceiver 63, theaccelerometer 67, the timer 66, the battery 62 and memory 65.

The asset tracking system 100 includes a server 40 that is connected tothe network 10. The server 40 may be configured to determine thelocations of one or more of the mobile devices 20 and perform thecomputational work in estimating the locations of asset tags 60 withinthe indoor facility 110. In at least some embodiments, the server 40 maybe implemented as a collection of a plurality of server computers. Theserver 40 may include a memory 41, a processing unit 42 and acommunication subsystem 43. In some embodiments, the memory 41 may storedevice information for one or more of the mobile devices 20 and theirassociated locations within the indoor facility 110. For example, thememory 41 may contain a database 46 of managed mobile devices 20 in theindoor facility 110. For a managed mobile device 20, the database 46 mayindicate one or more of: a device identifier (e.g. serial number, phonenumber); a user associated with the device 20; history of visitedlocations in the indoor facility 110 (including associated timestamps);and a current location of the device 20. The memory 41 may optionallystore map data identifying the current locations of the managed mobiledevices 20. In some cases, the server 40 may not have device informationfor the mobile devices 20 in the indoor facility 110. In other words,when a mobile device 20 in the indoor facility 110 detects a wirelesssignal from an asset tag 60, the mobile device 20 may be configured toestablish a connection to the server 40 for the first time and transmitdevice information for the mobile device 20 to the server 40 forprocessing by the server 40.

The server 40 of the asset tracking system 100 has access to an assetsdatabase 45. The assets database 45 may be stored in the memory 41, orremotely accessed by the server 40 for retrieving and updating dataassociated with the assets 50. In at least some embodiments, the assetsdatabase 45 contains a record of the assets 50 that are known to be oridentified (for example, by one or more entities) as being deployed inthe indoor facility 110 and stores various useful information pertainingto the assets 50. For example, the assets database 45 may contain datarelating to a plurality of deployed assets 50, including, but notlimited to: asset identifiers (e.g. type of asset); age of the asset;identifiers for an associated asset tag; registration status of theasset tag and/or asset; history of visited locations and associatedtimestamps; current location of the asset; identifiers of mobile devicesthat reported detected signals from the associated asset tag; firstdate/time of tracking; last date/time of location update; asset-userassociations; maintenance information for the asset; and last date/timeof change of battery of the associated asset tag.

The processing unit 42 may include a single processor with multiplecores or multiple processors (with single or multiple cores). Theprocessing unit 42 interacts with the communication subsystem 43 toperform communication functions via the network 10 with other systems,servers and/or devices such as the mobile devices 20.

In at least some embodiments, the server 40 may have access to orimplement an indoor positioning system for the facility 110. The server40 may connect to and retrieve location data for the mobile devices 20from an indoor positioning system. The indoor positioning system may,for example, be a system based on wireless AP fingerprints within thefacility 110. The server 40 may itself implement the indoor positioningsystem or request location data associated with one or more mobiledevices 20 from a separate indoor positioning system. That is, thelocation associated with a mobile device 20 in the facility 110 may bedetermined directly by the server 40 or a separate system to which theserver 40 has access for sending and retrieving data.

Registration of Asset Tags

Reference is now made to FIG. 2, which shows, in flowchart form, aserver-implemented method for automatically registering an asset tag inassociation with an asset in a database. In at least some embodiments,the method 200 may be implemented by a server, such as the server 40 ofFIG. 1. By way of example, the method 200 may be implemented by a MobileDevice Management server which manages a plurality of mobile devicesdeployed in an enterprise environment. In particular, the server iscommunicably connected to the mobile devices in an indoor facility of anenterprise via a wireless network, such as a WLAN.

An asset tag associated with a deployed asset is configured to broadcastwireless signals to enable tracking of the asset. For example,processing circuitry of the asset tag may cause one or more wirelesstransceivers of the asset tag to broadcast wireless beacon signals. Inat least some embodiments, the wireless transceiver of the asset tag maybroadcast signals when the asset is first deployed in the indoorfacility. In particular, the asset tag may be affixed to the asset atthe time the asset is deployed. Broadcasting by the asset tag upon firstdeployment of the asset may allow the asset to be tracked from the startof its deployment and facilitate the server's determination of aninitial location of the asset. In some other embodiments, wirelesssignals may be broadcast by an asset tag when the asset tag firstbecomes operational. For example, if the asset is retrofitted with anasset tag after the asset had already been deployed in the indoorfacility, when the asset tag is first activated, the processingcircuitry may cause wireless beacon signals to be broadcast.

The signals transmitted by an asset tag may represent various differenttypes of data. In particular, a broadcast signal may represent dataabout the asset tag, including, without limitation: identifier of theasset tag; product or manufacturer code; current battery status; andtime of transmission of the wireless signal. In some embodiments, thebroadcast signal may represent other information relating to the assettag and/or the associated asset. For example, the signal may indicatethat there is some problem with the asset (e.g. asset is being removedfrom a designated space) or the asset tag (e.g. asset tag ismalfunctioning).

In at least some embodiments, transmission of the broadcast signal mayoccur continuously at a predetermined rate. In particular, theprocessing circuitry of the asset tag may be programmed to establish afixed transmission rate for the broadcast signal and to control thewireless transceiver to broadcast at the fixed rate.

In some embodiments, the transmission rate may be variable. For example,the transmission rate may depend, in part, on the remaining charge forthe battery associated with the asset tag. If the remaining charge ofthe battery falls below a threshold level, the transmission rate of thebroadcast signal may be decreased. In some embodiments, the transmissionof the wireless signal may switch between a fixed rate and a variablerate. The asset tag may continue to broadcast the signal until anexplicit instruction is received to cease transmission of the signal. Adegree of randomness in the frequency of broadcasts may be employed forcollision avoidance in some embodiments.

One or more mobile devices that come within range of a signal broadcastby the asset tag may detect the signal. It will be appreciated that bothstationary (i.e. at-rest) and moving/travelling devices within theindoor facility may be capable of detecting the broadcast signal fromthe asset tag. Upon detecting a broadcast signal from the asset tag, amobile device may generate an asset tag collision report. An asset tagcollision report is generated by a mobile device following detection of,or “collision” with, a wireless signal broadcast by an asset tag. Inparticular, an asset tag collision report includes an identifier of theasset tag associated with a tracked asset. As a mobile device may detecta plurality of broadcast signals transmitted by the asset tag, an assettag collision report may include a timestamp associated with each signalreceived by the mobile device from the asset tag. The asset tagcollision report may also include an RSSI associated with each of thereceived signals. In some embodiments, the mobile device may generateone asset tag collision report for each received broadcast signal fromthe asset tag. In particular, each time a broadcast signal from theasset tag is detected, the mobile device may generate an asset tagcollision report, indicating, at least, a timestamp and an RSSIassociated with that signal. In some other embodiments, the mobiledevice may generate one asset tag collision report that contains datafor a plurality of received broadcast signals. The asset tag collisionreport may also include an identifier of the mobile device thatgenerated the report. That is, the asset tag collision report mayindicate the identity (e.g. device ID/user/etc.) of a reporting mobiledevice from which the asset tag collision report originated.

In at least some embodiments, an asset tag collision report may specifya location of a mobile device associated with a time at which abroadcast signal from the asset tag is received by the mobile device.That is, the asset tag collision report may identify a location withinthe indoor facility at the time when the mobile device detected abroadcast signal transmitted by the asset tag. For example, the locationinformation provided in an asset tag collision report may indicate adefined area (e.g. room) of the indoor facility in which the mobiledevice is located when a signal from the asset tag is detected.

When a broadcast signal is detected by a mobile device, an indoorpositioning application on the mobile device may be used to identify alocation of the mobile device associated with the timestamp for thedetection of the signal. Where an asset tag collision report includesdata for multiple received broadcast signals, the report may indicate alocation of the mobile device associated with each of the receivedsignals. In some embodiments, the asset tag collision report may includedata that can be used by an indoor positioning system to determine alocation of the mobile device within the facility at the time when themobile device detected a broadcast signal from the asset tag, withoutexpressly indicating a specific location of the mobile device within thefacility. For example, the asset tag collision report may include RSSImeasurements for wireless signals from a plurality of APs that arereceived by the mobile device, which measurements can be used by anindoor positioning system to identify a specific location in the indoorfacility. In some embodiments, the server may be configured to determinea three-dimensional position of the reporting mobile device within adefined area of the facility. For example, an asset tag collision reportfrom a mobile device may indicate a height of the mobile device aboveground when a signal from an asset tag is received at the mobile deviceor include RSSI measurements for signals from APs which allow a serverto compute the height of the mobile device above ground.

Mobile devices that detect wireless signals broadcast by an asset taggenerate and transmit asset tag collision reports to a server. Morespecifically, in operation 202, a server (e.g. MDM server) receives oneor more asset tag collision reports from at least one mobile device inthe indoor facility. The server may receive asset tag collision reportsfrom multiple different reporting devices which encounter broadcastsignals from the asset tag, or receive multiple asset tag collisionreports from a single reporting device that detects broadcast signalsfrom the asset tag.

In operation 204, the server determines the location of the asset tag inthe facility based on the one or more received asset tag collisionreports. In at least some embodiments, the server may determine thelocations of reporting mobile devices that transmit asset tag collisionreports to the server. For example, if an asset tag collision reportincludes an identifier of the mobile device that transmitted the report,the server may use an indoor positioning system for the facility todetermine the location of the mobile device based on the identifier. Insome other embodiments, an asset tag collision report may itselfindicate the location of the mobile device that transmitted the report.

The server may have access to a collisions history record of all assettag collision reports received from mobile devices in a facility. Forexample, the server may maintain a collisions history record in whichthe entries are organized by timestamps associated with detected signals(e.g. time of transmission of broadcast signal by asset tag) asindicated in the received asset tag collision reports. In particular,for each time, the collisions history record may specify the identitiesof the mobile devices that detected a signal broadcast by the asset tag,as well as other relevant information about the respective receivedsignal (e.g. RSSI). Where an asset tag collision report includes thelocation of the mobile device that generated and transmitted the report,the collisions history record maintained by the server will also specifythe location of the mobile device in association with the time at whichthe mobile device detected a broadcast signal from the asset tag. Basedon this crowd-sourced approach, the server may be able to collectsufficient amount of data from the asset tag collision reports todevelop and refine an estimate of a location of the asset tag within thefacility. That is, determining the location of the asset tag maycomprise obtaining an estimate of the location based on data accumulatedfrom the received asset tag collision reports.

A technique which may be employed for deriving estimates of the assettag's location is trilateration. Given two independent measurements ofdistance from the asset tag to mobile devices with known locations, thelocation of the asset tag can be narrowed to two possibilities, and anyadditional information (e.g. a third distance measurement to a thirdmobile device with a known location) may uniquely identify the assettag's location. In some embodiments, the system may use one or moresignal parameters to assist in location determination. For example, anRSSI for the signal broadcast by the asset tag may be used to determinean estimated distance to a receiver from the source of the signal. Whileaccurate distances may generally not be obtained using signal parametersalone, several indoor localization systems based on signal parametershave been successfully implemented. Such systems are described in, atleast, “An indoor bluetooth-based positioning system: Concept,implementation and experimental evaluation.” (Silke Feldmann,Kyandoghere Kyamakya, Ana Zapater, and Zighuo Lue. InternationalConference on Wireless Networks, pages 109-113, 2003), “Indoorlocalization using Bluetooth.” (Tiago Fernandes., 6th Doctoral Symposiumin Informatics Engineering, pages 480-483, 2011), both of which areincorporated herein by reference. A simplified distance estimation modelis given in “Accuracy of Location Identification with AntennaPolarization on RSSI” (Xu Huang, Mark Barralet, Dharmendra Sharma.Proceedings of the International Multi- Conference of Engineers andComputer Scientists, 2009) by equation (1):

RSSI=−(10×n)log₁₀ d−A  (1)

where RSSI is measured in dBm, n represents a path loss exponent (whichdepends on the propagation characteristics of the received signal), d isdistance in meters between a transmitter and a receiver and A is areference RSSI at a distance of 1 meter from the transmitter. In orderto use equation (1), the values of n and A may be determinedempirically. Other localization algorithms using trilateration may beused by the server to develop estimates of the location of the asset tagbased on data from a plurality of (i.e. at least three) asset tagcollision reports.

With each receipt of an asset tag collision report, the server may usethe additional data from the report to refine the computation of anestimate of the asset tag's location. In at least some embodiments, theserver may include an asset tag location estimation module that isconfigured to apply a suitable localization algorithm to data from aplurality of received asset tag collision reports. For a specifictimestamp in the collisions history record maintained by the server, theserver may use the one or more entries corresponding to the timestamp todetermine the location of a mobile device that detected a broadcastsignal from the asset tag and an RSSI of the detected broadcast signal.The server may extract the location information of the mobile devicefrom the asset tag collision report itself or access an indoorpositioning system for the facility in order to identify a locationcorresponding to the mobile device using the device's identifier(specified in the asset tag collision report). For example, if the assettag collision report includes RSSI measurements for wireless signalsreceived by the mobile device from a plurality of APs within thefacility, the indoor positioning system may correlate the RSSImeasurements with wireless AP fingerprints for the facility in order todetermine the location of the mobile device. The location of the mobiledevice and the RSSI of the broadcast signal from the asset tag that themobile device detects can be input to the asset tag location estimationmodule to determine the location of the asset tag at the relevant time.

In some cases, the server may not have sufficient data for atrilateration-based localization technique. For example, the server mayreceive no more than two asset tag collision reports from mobile devicesin the facility. In such cases, the server may be configured to collectcontext data about the facility to determine an estimated location ofthe asset tag. For example, if the server only receives location datafrom two mobile devices detecting a broadcast signal, reducing thenumber of possible locations of the asset tag to two, the server mayaccess an indoor positioning system for the facility and determine thatone of the possibilities is an inaccessible location, thus eliminatingthe possibility as a viable location for the asset tag. As a furtherexample, the server may reject those scenarios in which an asset tag isdetermined to be possibly located in a washroom or an unoccupied space(e.g. vacant room) in the facility. In some embodiments, the server mayextrapolate a location of an asset tag by forming a trajectory of theasset tag's traveled path or by using a dead reckoning technique.

Even if highly accurate measurement of distances is not obtained basedon the RSSI measurements, the server may nevertheless be capable ofidentifying a defined area of the facility in which the asset tag islocated. In particular, the server may be able to localize the asset tagto floor- or room-level. That is, even if the exact location of theasset tag within the facility cannot be derived based on data from theasset tag collision reports, a room (or passage, workspace, etc.) inwhich the asset tag is located may be determined (for example, throughtrilateration and contextual deduction).

In formulating estimates of the location of an asset tag based on datafrom a plurality of asset tag collision reports, the server may beconfigured to apply suitable weightings to received signal measurementdata. In particular, in a triangulation-based localization algorithm,the server may place greater weight on the locations of some reportingmobile devices than the locations of other reporting mobile devices. Forexample, if a particular mobile device receives multiple (i.e. two ormore) signals from an asset tag, the location(s) of that mobile devicemay be accorded more weight in a localization algorithm than anothermobile device which reports only a single detected signal from the assettag. By way of further example, if a mobile device reports a highmagnitude RSSI for a received signal, greater weight may be placed onthe location(s) of that mobile device compared to other mobile devices.Other criteria for distribution of weights to the locations of differentreporting devices in the server's localization algorithm may beavailable.

In operation 206, the server selects a first asset from a set of one ormore unregistered assets that are known to be or identified as beingdeployed in the indoor facility, based on determining that there is amatch between the location of the asset tag and location informationassociated with the first asset. Similar to the server 40 of FIG. 1, theserver has access to an assets database which stores informationassociated with assets that are known to be deployed in the facility. Inparticular, the assets database contains, among others, informationrelating to deployed assets that are yet to be registered in associationwith an asset tag. For example, the assets database may indicate, foreach of a plurality of deployed assets, a registration status of theasset. In at least some embodiments, the assets database may specify,for each unregistered asset, a defined area (e.g. room) in the facilityin which the unregistered asset is located. When the server determinesthat an asset tag is located in a certain defined area (i.e. based onasset tag collision reports transmitted by one or more mobile devices),and if the defined area is known to contain only a single unregisteredasset, the asset tag and the unregistered asset in the defined area canbe paired. That is, the server may select the unregistered asset locatedin the defined area as the asset to be paired with the asset tag.

Where an asset tag is determined to be in a certain defined area, butthe defined area is known to contain two or more unregistered assets,the server may use contextual data relating to the unregistered assetsand/or the defined area to deduce an appropriate pairing of the assettag with an asset. For example, if an unregistered asset tag isdetermined to be located in a particular room, and an assets databaseindicates that the room holds a plurality of unregistered assets, theserver may attempt to match the asset tag with one of the plurality ofunregistered assets. In at least some embodiments, the server may haveaccess to floor plans of the facility that provide various informationabout a defined area (e.g. room, passage, etc.) such as its location,type/purpose, dimensions, and boundaries.

In at least some embodiments, the type/class of an asset, as indicatedin an assets database, may be used to inform where the asset is likelyto be located in a defined area. For example, assets that are used forvisual display of information, such as flat-panel displays, projectorscreens, etc., are often positioned on or proximal to one of theinterior walls of a room. If an asset tag is determined to be near aninterior wall of the room and at least one of the unregistered assets inthe room is a visual display device, the server may match/assign theasset tag to the unregistered display device or, at least, reduce thenumber of possible assets which may be paired with the asset tag. As afurther example, assets such as fire extinguishers and wall-mount phonesmay often be located near an entrance/exit of a room. Thus, if an assettag is determined to be near an entrance/exit, the server may select theappropriate asset that is likely to be by the entrance/exit as the assetto be paired with the asset tag. Other structural features of a definedarea, such as windows, closets, etc., which may be identified by theserver based on information that is accessible to the server (e.g.detailed floor plans) may inform the process of matching asset tags withcontextual data associated with unregistered assets.

In some cases, the server may detect that there are two or moreunregistered asset tags in a single defined area. For example, aplurality of asset tag collision reports transmitted by mobile devicesin a single room may indicate the presence of two or more differentasset tags that have not been registered (i.e. the asset tag identifiersare not stored in database). In such scenarios, the server may useinformation identifying the relative locations of the unregistered assettags to deduce appropriate pairings with assets in the defined area. Forexample, if two or more asset tags are located near an entrance/exit toa room, the server may determine which of the assets tags is positionedclosest to the entrance/exit and designate that asset tag as beingassociated with an asset that is known to be typically located byentrances/exits (e.g. fire extinguisher).

In operation 208, the asset tag is registered in association with theselected first asset in a database. In at least some embodiments, whenan appropriate pairing of an unregistered asset tag with a first assetis determined by the server, the server may update an assets database,such as database 45 of FIG. 1, by indicating the association between theasset tag and the first asset in the database.

Reference is now made to FIG. 3, which shows another example method 300for automatically registering an asset tag in association with a trackedasset. In at least some embodiments, the method 300 is implemented by aserver, such as server 40 of FIG. 1.

Operation 302 of method 300 corresponds to the operation 202 of FIG. 2.More specifically, the server receives one or more asset tag collisionreports from at least one mobile device that detects wireless broadcastsignals transmitted by an unregistered asset tag. For example, theserver may receive asset tag collision reports from one or more mobiledevices that are either located inside or in the vicinity of a definedarea (e.g. room) in which an asset tag is located. In operation 304, theserver determines a three-dimensional position of the asset tag in thedefined area within which the asset tag is located. In particular, basedon a plurality of received asset tag collision reports, the server maydetermine a height of the asset tag above ground in the defined area.For example, if the server is able to determine the three-dimensionalpositions (e.g. height) of those mobile devices that report collisionswith an unregistered asset tag, an approximate three-dimensionalposition of the asset tag within a room may be computed by the server,based on the RSSI of signals received by the reporting mobile devicesfrom the asset tag (i.e. according to a collisions history recordcompiling data from multiple asset tag collision reports). In somecases, the height of the asset tag may be computed as a relative height.For example, the server may be able to infer that a certain unregisteredasset tag is located at a higher/lower altitude relative to a reportingmobile device, a registered asset, another unregistered asset tag, etc.As another example, the height of an asset tag may be expressed in otherrelative terms: an asset tag may be closer to the ceiling than to thefloor, closer to the floor than the ceiling, etc.

In operation 306, the server selects a first asset to be paired with theunregistered asset tag based on determining that there is a matchbetween the three-dimensional position of the asset tag and a probablethree-dimensional location of the first asset. In particular, the serverdetermines a probable three-dimensional position of the first assetbased on known information, such as information stored in an assetsdatabase, about the first asset. For example, assets such as overheadprojectors or light fixtures are likely to be positioned near theceiling of a defined area. That is, based on the type/class of an asset,the probable three-dimensional position of the asset may be determined,either in absolute or relative terms. Thus, if a room in a facility isknown to contain an overhead projector or light fixtures, anunregistered asset tag which is positioned at a height that is close tothe ceiling of the room may be paired with the projector/fixtures.

In some embodiments, the probable three-dimensional position of an assetin a defined area may be inferred based on the position and/ordimensions of other assets that are known to be located in the samedefined area. For example, if a table is known to be located in acertain room and its height and/or position is known (i.e. stored in theassets database) or can be estimated, the relative three-dimensionalpositions of assets that typically accompany the table (e.g.conferencing phone, chairs, etc.) can be ascertained. Thus, the probableposition of, for example, a conferencing phone in a room may becharacterized as being higher than table-level. In similar manners, aflat-panel display (e.g. television monitor) may be associated with aposition that is higher than table-level and proximal to an interiorwall of the room, and a projector device that is transported throughouta facility using a registered cart/stand may be associated with aposition that is higher than a known height of the cart/stand.

It should be noted that an asset is not required to be known or storedin a database for the asset to be paired with an unregistered asset tag.That is, an asset tag may be connected to an asset that is not known tobe or identified as being deployed in the facility and the presentsystem and methods may still provide useful tracking information for theunknown asset. For example, a boardroom in a facility is likely to hold,at least, a centrally disposed table and a plurality of chairspositioned along the periphery of the table. If an unregistered assettag is determined to be located in the boardroom and is not locatedgenerally near a center of the room, the server may infer that the assettag is associated with one of the plurality of chairs. Even if the chairto which the asset tag is connected cannot be identified exactly,knowing the class of asset that is tracked using the asset tag may proveuseful. For example, if after registration of the asset tag, the assettag is detected as being moved out of the boardroom, an asset trackingand management system may be so notified (i.e. a chair has been takenfrom the boardroom and moved to room X). Thus, the registration of anasset tag in association with an asset class/type can sometimes provideuseful information for tracking assets in a facility. Furthermore,information about assets that are known to be or identified as beingdeployed in a certain defined area can be used for determining thelocation and/or identity of an unregistered asset. For example, if aregistered asset (e.g. desktop computer) that is typically accompaniedby or used in conjunction with another unregistered asset (e.g. monitor)is known to be in a room, even if the unregistered asset is notidentified as being present in the room (for example, in an assetsdatabase), the server may be able to deduce that an asset tag that istransmitting broadcast signals from the room is associated with theunknown, unregistered asset.

In operation 308, the server registers the asset tag in association withthe selected first asset in a database, such as assets database 45 ofFIG. 1. It will be appreciated that one of the uses for a collisionshistory record is determining whether a detected asset tag is beingremoved from a defined area. In particular, even if an asset tag is notregistered in association with a specific asset or asset class, mobiledevices that detect signals broadcast by the asset tag may be able toprovide information for the server to determine whether the asset tag isleaving a defined area. For example, if an asset tag is determined to bein motion (e.g. based on RSSI measurements received by stationary mobiledevices) and nearing an exit of a room, it may be inferred that theasset tag (and by association, the tracked asset) is about to be removedfrom the room. In response to such detection by the server, an assettracking system may be configured to prompt a user device, employee,etc. that is currently near the asset tag to ensure that the asset tagis registered before relocation. In some embodiments, various geo-fencesmay be defined within a facility such that relocation of unregisteredasset tags can trigger generation of notifications or alerts to causethe asset tags to be properly registered.

Reference is now made to FIG. 4, which shows another example method 400for automatically registering an asset tag in association with a trackedasset. In at least some embodiments, the method 400 is implemented by aserver, such as server 40 of FIG. 1.

Operations 402, 404 and 406 of method 400 correspond to operations 202,204 and 206 of method 200, respectively. In particular, the serverselects a first asset that is to be paired with an unregistered assettag, based on determining that there is a match between the location ofthe asset tag and the location of the first asset, in operation 406. Inoperation 408, the server determines whether the pairing of the selectedfirst asset and the unregistered asset tag meets a predefined confidencethreshold. This determination in operation 408 may comprise a check ofthe accuracy of the determined location of the asset tag and/or a checkof the accuracy of a pairing of an unregistered asset tag with an asset,as will be explained in greater detail below.

In at least some embodiments, in operation 408, the server may perform acheck to determine whether an estimate of the location of the asset tagsatisfies a pre-determined confidence threshold. Various confidencethresholds may be appropriate for estimating the location of an assettag. For example, the confidence threshold may be satisfied if more thana threshold number of asset tag collision reports from different mobiledevices is received by the server for a certain time. As a furtherexample, if more than a threshold number of signals is received by asingle mobile device, the mobile device may correspond to a user who isphysically moving the asset associated with the asset tag, suggestingthat an estimate of the asset tag's location based on a current locationof the user's mobile device is likely to be accurate. The server mayalso consider other factors in determining that an estimate of the assettag's location is confidently correlated to its actual location,including the state of motion of the asset tag (i.e. whether the assetis in motion or at rest) and magnitude of RSSI of received signals. Insome embodiments, a memory associated with the server may store one ormore pre-determined rules regarding confidence thresholds for estimatesof an asset tag's location.

When a certain defined area is known to contain a plurality ofunregistered assets, it may be difficult to determine an accuratepairing of an unregistered asset tag with one of the plurality of assetsin the defined area. For example, if multiple different assets arepositioned close together in a room, have similar three-dimensionalpositions (e.g. similar heights), or are of similar or same type/class,it may not be possible to derive a pairing of an unregistered asset tagwith one of the multiple assets to a desirable degree of accuracy. Inparticular, an accurate pairing may not be possible based on locationmetrics or available contextual data about the defined area and theassets. In at least some embodiments, the server may perform a check todetermine whether a pairing of an unregistered asset tag with a selectedasset meets a confidence threshold. For example, a confidencemetric/value associated with a pairing may be derived based on numerousfactors, including, but not limited to: type/identity of defined area;class of selected asset; three-dimensional position of the selectedasset; number of unregistered assets in the same defined area as theselected asset; and number of unregistered assets of the same class asthe selected asset in the defined area.

If the pairing of the selected first asset with the unregistered assettag is determined to satisfy a suitable confidence threshold, the serveris configured to register the asset tag in association with the firstasset, in operation 410. If, on the other hand, the pairing does notmeet the confidence threshold, the server may transmit messages to oneor more user devices deployed in the facility, requesting users of theuser devices to confirm whether the pairing is correct, in operation412. In particular, the server may be configured to automatically sendrequests to people who are in the vicinity of the asset tag to verifythat the asset tag has been correctly paired with the asset that it istracking. In at least some embodiments, the server may transmit messagesto user devices which are determined to be in close proximity to theasset tag. The server may select such user devices by, for example,accessing an indoor positioning system to locate those mobile deviceswhose locations are proximal to the location of the asset tag. Forexample, the user devices may include mobile devices that are determinedto be in the same room (or passage, etc.) of the facility as the assettag. As a further example, the user devices may include those mobiledevices from which the server received asset tag collision reports basedon collisions with the asset tag.

The messages requesting confirmation of tag-to-asset pairings can bepresented on user devices in various different ways. For example, themessages may be in the form of emails, pings, or mobile appnotifications. In particular, a mobile app may be used to confirm atag-to-asset pairing. Use of such mobile apps may, for example, bemanaged by an MDM solution, such as an MDM server for an enterprise. Insome embodiments, the graphical user interface of a user device maypresent a list of unregistered assets and one or more asset tags thathave been detected (for example, based on asset tag collision reports).Identifying information for the assets, such as asset class, device ID(e.g. serial number), etc., as well as for the asset tag may bedisplayed.

These confirmation messages may be sent to user devices at variousdifferent times or upon occurrence of one or more predefined events. Insome embodiments, the messages may be sent to user devices that enterinto and/or currently occupy a defined area in which an unregisteredasset tag is located. For example, user devices of employees attending ameeting in a boardroom may be notified with requests to confirm possibletag-to-asset pairings for the asset tags that are determined to be inthe boardroom. In some embodiments, the confirmation messages may besent after a predetermined number of asset tag collision reportscorresponding to an unregistered asset tag are received at the server.For example, confirmation messages may not be sent until at least athreshold number of asset tag collision reports for an asset tag arereceived. In this way, the server may be given an opportunity to collectsufficient amount of data to perform the deduction of a tag-to-assetpairing on its own, without having to rely on confirmation from userdevices.

A user may input various information to reply to requests for atag-to-asset pairing confirmation. For example, various input interfacesof a user device may be used for selection and textual input. In someembodiments, a user device may be used to add previously unknown assetsto a database of deployed assets, by associating with an asset tag thatis detected by the user device. For example, when a user device detectssignals broadcast by an asset tag but the asset corresponding to theasset tag is not known to the server (i.e. not stored in an assetsdatabase), the user device may be presented with an option to manuallyregister the asset tag by adding the associated asset to the database ofdeployed assets. The user may, for example, capture an image of abarcode (e.g. Universal Product Code, two-dimensional barcode, etc.)associated with an asset and/or an asset tag in confirming atag-to-asset pairing or registering a previously unknown asset.

The confirmation messages can be sent to multiple different user deviceswhich may improve the reliability of tag-to-asset pairing verifications.In at least some embodiments, the server may register an asset tag inassociation with an asset upon receiving at least a predefined thresholdnumber of confirmations from user devices regarding the tag-to-assetpairing. If an indication is received from one or more user devices thata certain tag-to-asset pairing is incorrect, the server may beconfigured to automatically select a second unregistered asset that isknown to be or identified as being deployed in the facility and registerthe asset tag in association with the second asset. For example, if auser indicates that a pairing of an asset tag with a first asset isincorrect, the server may present the user with a list of one or moreunregistered assets that are likely to be associated with the detectedasset tag, such as those unregistered assets which may be in the samedefined area as the first asset. In some embodiments, the server may beconfigured to rank a set of unregistered assets according to theirlikelihood of being associated with a particular asset tag. Such rankingmay be defined based on data from one or more received asset tagcollision reports, and may usefully guide a user in finding the assetthat is associated with an asset tag. Alternatively, the user may berequested to manually enter identifying information for the asset thatis associated with the asset tag. For example, if the asset tag is notassociated with any of the known deployed assets or if it is moreexpedient for a user to manually enter a tag-to-asset pairing (e.g. whenthere is a large number of possible pairings), the user may optionallyinput the correct pairing information as a response to a request forconfirmation from the server.

By collecting data from a plurality of asset tag collision reports thatare based on collision with signals from an asset tag, the server canmaintain a record of signal detection events for the asset tag. Based onthis record of signal detection events, the server can obtain estimatesof the location of the asset tag. For example, if the server haslocation information for three or more devices that each detected abroadcast signal from the asset tag at a given time (or a range of time)and the signal strength information (i.e. RSSI) of the signal detectedby the respective devices, the server can perform trilateration todetermine an estimate of the location of the asset tag at the given time(or range of time). Using a crowd-sourced approach, the server canreceive asset tag collision reports from a plurality of mobile devicesor a plurality of asset tag collision reports from a single device todevelop and refine an estimate of the asset tag's location within thefacility. The location of the asset tag can, in turn, be matched to thelocation or probable location of an unregistered asset based, at leastin part, on known contextual data relating to the asset and/or thedefined area in which the asset tag is known to be located.

The various embodiments presented above are merely examples and are inno way meant to limit the scope of this application. Variations of theinnovations described herein will be apparent to persons of ordinaryskill in the art, such variations being within the intended scope of thepresent application. In particular, features from one or more of theabove-described example embodiments may be selected to createalternative example embodiments including a sub-combination of featureswhich may not be explicitly described above. In addition, features fromone or more of the above-described example embodiments may be selectedand combined to create alternative example embodiments including acombination of features which may not be explicitly described above.Features suitable for such combinations and sub-combinations would bereadily apparent to persons skilled in the art upon review of thepresent application as a whole. The subject matter described herein andin the recited claims intends to cover and embrace all suitable changesin technology.

The subject-matter of the disclosure also relate, among others, to thefollowing aspects and clauses:

-   -   Clause 1. A server-implemented method for registering an asset        tag in a database, the asset tag being used to track a location        of an asset in an indoor facility, the method comprising:        -   receiving, from at least one mobile device connected to the            server via a wireless communication network, one or more            asset tag collision reports, each of the one or more asset            tag collision reports including a tag identifier of the            asset tag, wherein the tag identifier is transmitted to the            at least one mobile device in wireless signals broadcast by            the asset tag;        -   determining a location of the asset tag based on the one or            more received asset tag collision reports;        -   selecting a first asset from a set of one or more            unregistered assets that are identified as being deployed in            the indoor facility based on determining that there is a            match between the location of the asset tag and location            information associated with the first asset; and        -   registering the asset tag in association with the first            asset in the database.    -   Clause 2. The method of clause 1, wherein the location        information associated with the first asset is retrieved from an        assets database storing information associated with the one or        more unregistered assets that are identified as being deployed        in the indoor facility.    -   Clause 3. The method of either clause 1 or 2, wherein        determining the location of the asset tag comprises identifying        a defined area of the indoor facility in which the asset tag is        located.    -   Clause 4. The method of any one of clauses 1 to 3, wherein the        defined area is a room in the indoor facility.    -   Clause 5. The method of any one of clauses 1 to 4, wherein        determining the location of the asset tag comprises identifying        a three-dimensional location of the asset tag within the defined        area and wherein selecting the first asset comprises determining        a probable three-dimensional location of the first asset based        on a type associated with the first asset.    -   Clause 6. The method of any one of clauses 1 to 5, wherein the        probable three-dimensional location of the first asset indicates        a probable height of the first asset above ground and wherein        determining that there is a match comprises determining that the        probable height of the first asset above ground matches a height        of the asset tag above ground within the defined area.    -   Clause 7. The method of any one of clauses 1 to 6, wherein each        of the one or more asset tag collision reports indicates an        identity of a reporting mobile device from which the asset tag        collision report originated.    -   Clause 8. The method of any one of clauses 1 to 7, wherein the        asset tag collision report identifies a location of the        reporting mobile device within the indoor facility at a time        when a wireless signal from the asset tag was detected by the        reporting mobile device.    -   Clause 9. The method of any one of clauses 1 to 8, wherein the        location of the reporting mobile device within the indoor        facility is determined by the reporting mobile device using an        indoor positioning application.    -   Clause 10. The method of any one of clauses 1 to 9, wherein the        identified location specifies a defined area of the indoor        facility.    -   Clause 11. The method of any one of clauses 1 to 10, wherein the        asset tag collision report includes a timestamp indicating a        time at which the wireless signal from the asset tag was        detected by the reporting mobile device.    -   Clause 12. The method of any one of clauses 1 to 11, wherein the        asset tag collision report includes a received signal strength        indicator (RSSI) of the wireless signal detected by the        reporting mobile device.    -   Clause 13. The method of any one of clauses 1 to 12, further        comprising:        -   determining that a pairing of the first asset with the asset            tag does not meet a predefined confidence threshold; and        -   in response, transmitting messages to one or more user            devices to request users of the user devices to confirm            whether the pairing is correct.    -   Clause 14. The method of any one of clauses 1 to 13, wherein the        one or more user devices comprise devices which are determined        to be in close proximity to the asset tag.    -   Clause 15. The method of any one of clauses 1 to 14, wherein the        one or more user devices comprises devices which are determined        to be in a defined area of the indoor facility in which the        asset tag is located.    -   Clause 16. The method of any one of clauses 1 to 15, wherein the        one or more user devices comprise devices from which one or more        of the asset tag collision reports originated.    -   Clause 17. The method of any one of clauses 1 to 16, further        comprising:        -   receiving, from at least one of the one or more user            devices, a message indicating that the pairing is incorrect;        -   in response,            -   selecting a second asset from the set of one or more                unregistered assets that are identified as being                deployed in the indoor facility; and            -   registering the asset tag in association with the second                asset in the database.    -   Clause 18. The method of any one of clauses 1 to 17, further        comprising maintaining a record of the one or more received        asset tag collision reports.    -   Clause 19. A system comprising:        -   an asset tag for use in tracking a location of an asset in            an indoor facility;        -   at least one mobile device configured to detect wireless            signals broadcast by the asset tag; and        -   a server connected to the at least one mobile device via a            wireless communication network, wherein the server is            configured to:            -   receive, from the at least one mobile device, one or                more asset tag collision reports, each of the one or                more asset tag collision reports including a tag                identifier of the asset tag, wherein the tag identifier                is transmitted to the at least one mobile device in                wireless signals broadcast by the asset tag;            -   determine a location of the asset tag based on the one                or more received asset tag collision reports;            -   select a first asset from a set of one or more assets                that are identified as being deployed in the indoor                facility based on determining that there is a match                between the location of the asset tag and location                information associated with the first asset; and            -   register the asset tag in association with the first                asset in a database.    -   Clause 20. A non-transitory computer-readable medium storing        processor-executable instructions for a server to register an        asset tag in a database, wherein the instructions comprise:        -   instructions to receive, from at least one mobile device            connected to the server via a wireless communication            network, one or more asset tag collision reports, each of            the one or more asset tag collision reports including a tag            identifier of the asset tag, wherein the tag identifier is            transmitted to the at least one mobile device in wireless            signals broadcast by the asset tag;        -   instructions to determine a location of the asset tag based            on the one or more received asset tag collision reports;        -   instructions to select a first asset from a set of one or            more unregistered assets that are identified as being            deployed in an indoor facility based on determining that            there is a match between the location of the asset tag and            location information associated with the first asset; and        -   instructions to register the asset tag in association with            the first asset in the database.

1. A method for registering an asset tag in a database, the methodcomprising: receiving, from at least one mobile device, one or moreasset tag collision reports, each of the one or more asset tag collisionreports including a tag identifier of the asset tag, wherein the tagidentifier is transmitted to the at least one mobile device in wirelesssignals broadcast by the asset tag; determining a location of the assettag based on the one or more received asset tag collision reports; andregistering the asset tag in association with the tag identifier and thedetermined location in the database.
 2. The method of claim 1, furthercomprising determining, based on the location, one or more classes ofassets, and wherein registering further includes registering the assettag in association with said one or more classes of assets.
 3. Themethod of claim 2, wherein the determining the one or more classes ofassets is based on the determined location and contextual data regardingthe location.
 4. The method of claim 3, wherein the determined locationincludes a determined height and wherein the contextual data includesdata per class prescribing likely height of an asset of that class. 5.The method of claim 1, wherein determining the location of the asset tagincludes identifying a defined area of the indoor facility in which theasset tag is located.
 6. The method of claim 1, wherein registering theasset tag further includes identifying an unregistered asset havingassociated location information, determining that the locationinformation for the unregistered asset matches the determined location,and registering the unregistered asset in association with the asset tagin the database.
 7. The method of claim 1, wherein each of the one ormore asset tag collision reports indicates an identity of a reportingmobile device from which the asset tag collision report originated. 8.The method of claim 7, wherein the asset tag collision report identifiesa location of the reporting mobile device within the indoor facility ata time when a wireless signal from the asset tag was detected by thereporting mobile device.
 9. The method of claim 8, wherein the locationof the reporting mobile device within the indoor facility is determinedby the reporting mobile device using an indoor positioning application.10. The method of claim 7, wherein the asset tag collision reportincludes a timestamp indicating a time at which the wireless signal fromthe asset tag was detected by the reporting mobile device.
 11. A serverfor registering an asset tag in a database, the server comprising: aprocessor; and memory storing processor executable instructions that,when executed by the processor, cause the processor to receive, from atleast one mobile device, one or more asset tag collision reports, eachof the one or more asset tag collision reports including a tagidentifier of the asset tag, wherein the tag identifier is transmittedto the at least one mobile device in wireless signals broadcast by theasset tag, determine a location of the asset tag based on the one ormore received asset tag collision reports, and register the asset tag inassociation with the tag identifier and the determined location in thedatabase.
 12. The server of claim 11, wherein the processor executableinstructions further cause the processor to determine, based on thelocation, one or more classes of assets, and wherein registering furtherincludes registering the asset tag in association with said one or moreclasses of assets.
 13. The server of claim 12, wherein the processor isto determine the one or more classes of assets based on the determinedlocation and contextual data regarding the location.
 14. The server ofclaim 13, wherein the determined location includes a determined heightand wherein the contextual data includes data per class prescribinglikely height of an asset of that class.
 15. The server of claim 11,wherein the processor is to determine the location of the asset tag byidentifying a defined area of the indoor facility in which the asset tagis located.
 16. The server of claim 11, wherein the processor is toregister the asset tag by identifying an unregistered asset havingassociated location information, determining that the locationinformation for the unregistered asset matches the determined location,and registering the unregistered asset in association with the asset tagin the database.
 17. The server of claim 11, wherein each of the one ormore asset tag collision reports indicates an identity of a reportingmobile device from which the asset tag collision report originated. 18.The server of claim 17, wherein the asset tag collision reportidentifies a location of the reporting mobile device within the indoorfacility at a time when a wireless signal from the asset tag wasdetected by the reporting mobile device.
 19. The server of claim 18,wherein the location of the reporting mobile device within the indoorfacility is determined by the reporting mobile device using an indoorpositioning application.
 20. The server of claim 17, wherein the assettag collision report includes a timestamp indicating a time at which thewireless signal from the asset tag was detected by the reporting mobiledevice.
 21. A non-transitory computer-readable medium storingprocessor-executable instructions that, when executed, cause a server toregister an asset tag in a database, wherein the instructions comprise:instructions to receive, from at least one mobile device, one or moreasset tag collision reports, each of the one or more asset tag collisionreports including a tag identifier of the asset tag, wherein the tagidentifier is transmitted to the at least one mobile device in wirelesssignals broadcast by the asset tag; instructions to determine a locationof the asset tag based on the one or more received asset tag collisionreports; and instructions to register the asset tag in association withthe tag identifier and the determined location in the database.